I was just dealing with this, in my case the issue was that my device was never registered in my developer account. I use the device for my day job, and it was registered to that account, but not on my personal one.
On top of that, I had some pending PLAs to accept.
I noticed all this when I changed from manual to automatic managed signing in Xcode. Once I set it to automatic, accepted the PLAs, and registered the device, I could run my app on my device with no issue.
Andy Ibanez
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for
Post
Replies
Boosts
Views
Activity
I figured it out thank to last year's Accelerating App Interactions with App Intents sample code.
Essentially you can inject your app's navigation model to the Intent by using dependencies, namely the @AppDependency property wrapper and the AppDependencyManager class.
As of Xcode 15.0.1, this is still happening.
Interesting, I have found that if you show a NavigationStack in your first view, push some contents into it, and then you push Switch to another element in your Sidebar, it won't crash, but your pushed views will stay there, covering the other selection's content. You can pop back and it won't crash.
struct SidebarEntryPointView: View {
@Binding var appNavigation: AppNavigation
var body: some View {
NavigationSplitView(columnVisibility: $appNavigation.navigationStyleColumnVisibility) {
List(selection: $appNavigation.rootView) {
NavigationLink(value: appNavigation.rootView) {
Label {
Text("Anime")
} icon: {
Image(systemName: "tv")
}
}
.tag(RootView.animeList)
NavigationLink(value: appNavigation.rootView) {
Label {
Text("Manga")
} icon: {
Image(systemName: "book")
}
}
.tag(RootView.mangaList)
}
} detail: {
switch appNavigation.rootView {
case .animeList:
NavigationStack(path: $appNavigation.animeListNavigationPath) {
Button("Click Me") {
appNavigation.animeListNavigationPath.append(NavigationElement.character(characterId: 34))
appNavigation.animeListNavigationPath.append(NavigationElement.staff(staffId: 33))
print(appNavigation.animeListNavigationPath)
//$firstTabNavigation.navigationPath += [.character(characterId: 23)]
//$firstTabNavigation.navigationPath.append(.staff(staffId: 23))
}
.navigationDestination(for: NavigationElement.self) { screen in
switch screen {
case .character(let characterId):
DummyCharacterView(id: characterId)
case.staff(let staffId):
DummyStaffView(id: staffId)
default:
Text("wat")
}
}
}
default: Text("No hay")
}
}
}
}
In this example, I have two sidebar elements, Anime and Manga. The app launches in the Anime selected state, and it has a button that pushes two views into the NavigationStack. If you push the button and then Switch the selection to Manga, it works (though you need to pop back to see the "no hay" view).
So this is probably caused by the NavigationStack somehow? Still something I hope to see addressed in Xcode 15.1.
We are still seeing this exact error in Xcode 12 (12A7209) and this is not fixed yet. Is there a different workaround that won't kill our app for a considerable amount of devices?
Sorry for reviving this, but I saw my question here after registering to the new forums, and I thought I could update based on my findings.
The from parameter of uploadTask(with:from:completionHandler) cannot be nil. While the signature of the method does mark from as a Data?, the task gets automatically cancelled when it is missing/nil.
I have had a radar on this for a few years (FB5986524), but I never got any response.